Error in logs: failed to run timer #13030
Labels
pending author feedback
Waiting for the issue author to get back to a maintainer with findings, more details, etc...
stale
Is there an existing issue for this?
Kong version (
$ kong version
)3.5.0
Current Behavior
We are seeing a lot of those errors in the logs and don't know where they're coming from:
40#0: *2660424 [lua] job.lua:284: execute(): [timer-ng] failed to run timer unix_timestamp=1715723899267.000000;counter=2046305:meta=debug off: /usr/local/share/lua/5.1/resty/timerng/init.lua:405: expected `interval to be a number
I tried checking the Kong code as well as Openresty and the timer, but couldn't find where this is coming from. I don't know what the impact of this is other than very spammy logs.
Is there a way to get more logs or a full stack trace?
Could this be from the rate limiting plugin?
Expected Behavior
I expect to not have this log emitted.
Steps To Reproduce
No response
Anything else?
Kong running on Kubernetes
The text was updated successfully, but these errors were encountered: